Skip to content
This repository has been archived by the owner on Jun 20, 2023. It is now read-only.

fix: don't dag.Get in ResolveToLastNode when not needed #1

Merged
merged 1 commit into from
Aug 6, 2018

Conversation

magik6k
Copy link
Member

@magik6k magik6k commented Aug 2, 2018

Currently when trying to resolve path that points directly at an 'invalid' block, resolving will fail:

Error: failed to decode Protocol Buffers: incorrectly formatted merkledag node: unmarshal failed. proto: illegal wireType 7

This is a problem for block coreapi - ipfs/kubo#5331 (it works with this patch applied)

@magik6k magik6k requested a review from Stebalien August 2, 2018 08:51
@whyrusleeping
Copy link
Member

@magik6k could you add a test for this one?

@magik6k
Copy link
Member Author

magik6k commented Aug 6, 2018

Added some

@whyrusleeping whyrusleeping merged commit 34251f0 into master Aug 6, 2018
@whyrusleeping whyrusleeping deleted the fix/resolve-last-cid branch August 6, 2018 17:25
Stebalien added a commit to ipfs/kubo that referenced this pull request Aug 7, 2018
see: ipfs/go-path#1

License: MIT
Signed-off-by: Steven Allen <[email protected]>
Stebalien added a commit to ipfs/kubo that referenced this pull request Aug 7, 2018
see: ipfs/go-path#1

License: MIT
Signed-off-by: Steven Allen <[email protected]>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants